feat: add fastCRW tool#363
Open
us wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds fastCRW as a web scrape/search provider, alongside the existing Firecrawl integration — additive only, Firecrawl untouched.
Why
fastCRW is a self-hostable, fully open-source (AGPL) web engine — single ~8MB Rust binary, ~6MB RAM.
Runs 100% locally with full capability. Anti-bot/stealth, BYO-proxy + rotation, and JS rendering (Cloudflare JS-challenge, SPA) all ship in the open core. Firecrawl's OSS self-host gates its stealth engine (
fire-engine) behind a cloud-only flag, so its self-hosted instance falls back to plain fetch/Playwright and can't reliably reach protected or JS-heavy pages. fastCRW's open binary has no such gap.Faster and higher-recall on Firecrawl's own benchmark dataset. Truth-recall 63.74% vs 56.04%; median latency p50 ~1.9s vs ~2.3s. One binary, no multi-service stack.
On web search specifically: crw is not an alternative to SearXNG, it is built on top of it. SearXNG is the metasearch aggregator underneath; crw adds a quality layer on top: query expansion (multi-variant rewrite), content-aware reranking (re-scoring by fetched content instead of SearXNG's content-blind ordering), and category routing (research queries fan out to arxiv/semantic scholar/google scholar, code queries to GitHub). So you get SearXNG's breadth plus a measurable accuracy layer — all open-source (AGPL) and self-hostable with configurable engines.
Key via
CRW_API_KEY(free tier at https://fastcrw.com/dashboard); self-host base URL supported. Happy to adjust to your conventions — I maintain the integration and can provide free credits to evaluate.Because fastCRW is Firecrawl-API-compatible, the integration diff is tiny and purely additive — that's why it mirrors the Firecrawl wiring with minimal code.